@filigran/chatbot 3.10.0 → 3.11.1

package/README.md

@@ -88,6 +88,10 @@ import { ChatPanel } from '@filigran/chatbot';
 | `contextUsageEnabled` | `boolean`                               | `true`       | Show how full the model's context window is for the current conversation (ring + percentage in the composer toolbar). Data-driven, so it stays absent until the backend reports occupancy — see [Context usage](#context-usage). |
 | `composerToolbar`   | `React.ReactNode`                         | —            | Extra controls appended to the composer toolbar. The escape hatch for host-specific affordances (XTM One's session-tool picker) — the package never learns what they are. Pass nothing and the toolbar simply has none. |
 
+Plain-data props (`requestHeaders`, `apiEndpoints`, `pageContext`, `promptSuggestions`) are compared by content and callback props are called
+through a stable wrapper, so building them inline is fine. `t` and `logoIcon` are used as given: keep them stable (`useCallback` / `useMemo`),
+or every render of the host re-renders every message in the thread.
+
 #### Resizable Sidebar Example
 
 ```tsx
@@ -667,6 +671,7 @@ Every key the package can ask for, grouped by where it appears:
 - `'Enter to send now · Esc to stop'`
 - `'Files uploading...'`
 - `'Insert prompt template'`
+- `'Listening...'`
 - `'No prompt matches'`
 - `'Search prompts...'`
 - `'Send now'`
@@ -832,10 +837,14 @@ the suggestions route is unavailable the host's `promptSuggestions` prop is used
 instead, so the section is never empty.
 
 Dictation needs no configuration at all: it uses the browser's own Web Speech
-API, so the mic button appears wherever the API exists and is simply absent
-elsewhere. Finalised phrases are appended to the composer (never replacing a
-draft), interim words preview beside the button, and sending stops the mic so
-the next words cannot land in a composer the user just emptied.
+API, so the mic button appears inside the text field, next to Send, wherever
+the API exists and is simply absent elsewhere. It is not a toolbar item, so it
+never adds the toolbar row on its own. While it listens the field turns red and
+reads `Listening...`, finalised phrases are appended to the composer (never
+replacing a draft), interim words preview in the line under it, and every send
+(Enter, Send, Send now) stops the mic and drops the phrase still being
+recognised, so no words can land in a composer the user just emptied. Stopping
+the mic by hand keeps that last phrase.
 
 ### Context usage
 
@@ -947,6 +956,11 @@ returned byte-identical.
 - `remark-breaks` >= 4
 - `remark-gfm` >= 4
 
+## Dependencies
+
+- `unified` ^11 and `remark-parse` ^11 — the ranges react-markdown 10 depends on, so a host resolves them to the copies it already has. The panel
+  uses them to find the top-level blocks of a streaming answer, and re-renders only the blocks that can still change.
+
 ---
 
 ## Development
@@ -964,6 +978,12 @@ To build:
 yarn build
 ```
 
+To run the unit tests (Node's built-in test runner, which runs TypeScript natively from Node 22.18 / 23.6):
+
+```bash
+yarn test
+```
+
 To publish:
 
 ```bash